IBM Books

Nways Manager for HP-UX Installation Guide

Configuring Nways Manager Applications

This section describes any additional configuration steps that you need to perform after installing Nways Manager for HP-UX.
Important

Before configuring Nways Manager applications, be sure that you have installed the patches listed in Required Patches.

Configuring ATMC

To configure ATMC, complete this procedure:

  1. To run Java Development Kit (JDK) 1.17.01 or later, enter the following command to export the JAVA_HOME system variable:

    		export JAVA_HOME=/opt/java


  2. Install ObjectStore with the following patches:

    		PHSS_15391 PHSS_16585
  3. Change the following environment settings:
    1. Add the following lines to your /etc/profile file.

      		OS_ROOTDIR=/usr/local/ODI/0S5.1

      		SHLIB_PATH=/usr/local/ODI/0S5.1/lib

      		JAVA_HOME=/opt/java


    2. Add the following lines to your /.profile file:

      		PATH=$PATH:/usr/local/ODI/0S5.1

      		SHLIB_PATH=/usr/local/ODI/0S5.1/lib

      		JAVA_HOME=/opt/java

      		OS_CACHE_SIZE=5,000,000

      		OS_ROOTDIR=/usr/local/ODI/OS5.1

      		OS_COMMSEG=/usr/CML/OSTORE/CACHE

      		OS_CACHE_DIR=/usr/CML/OSTORE/CACHE


    3. Run the etc/environment file to make the changes effective.

Configuring Element Manager

The Element Manager component requires no additional configuration.

Accessing the Device Managers from a Web Browser

There are three basic components involved in Web browser-based access to the device managers:

Nways Manager Workstation

The Nways Manager maintains the Nways Web pages that are sent from the Web server to the Web browser clients.

Web Server

You can run Java device management applications in client mode on stations connected to the network management station without configuring a Web server, but for true intranet access through a Web browser, you must configure your Web server to locate the Nways Java Management Web pages subdirectory.

Web servers supported for the Nways Web access include:

On the network management station, you must:

  1. Assign a new port number for use by the HTTP server higher than 8000. (The default value is 80.) This action adds an additional level of security to Web browser access, and prevents port conflicts with other applications using the server.
  2. Assign an alias or logical name to the directory in which the HTML pages are stored on the management system. The Nways Web pages are stored in: 
    /usr/CML/JMA/java/websvr.
  3. Verify that the properties assigned to this directory by the server include allowing Web browser access. Consult your Web server documentation for more information on how to do this.

Web Access for ATM Manager

Before you can use the ATM Manager via a Web browser, you must configure your Web server. The following configuration for the Lotus Domino server can be used as a guide if you are using another server.

  1. Enter the following commands in the configuration file of your Web server, making sure that the two "Pass" statements are entered in this order: 
       Exec           /atm-bin/*      /usr/CML/ATMWEB/bin/*
   Pass           /atm-html/*     /usr/CML/ATMWEB/html/*
   Pass           /*              /a directory path/*
  2. Reset the Web server by entering the appropriate command; for example: 
       refresh -s httpd

Web Browser Compliant with JDK 1.1.5 or Later

Java support comes with your browser. The Web browser can dynamically load the Java application.

Java communication uses the IP host name and not the IP address, therefore both the client and server need the correct host names to which they are communicating. If the client is dynamically assigned an IP address, ensure that this IP address is associated with your client's IP host name. This process works correctly with Dynamic Host Configuration Protocol (DHCP).

If your client uses the PPP protocol to connect to the server, the client will be dynamically assigned both an IP address and an IP host name. In this situation, Windows NT(R), or Windows 95) do not provide the correct IP host name to the Java applications running in the client. Hence, the Java applications will not provide the correct IP host name to the server and the server will not be able to send asynchronous (unsolicited) events to the client. To correct this problem, change the IP host name on the Windows client to the value "localhost" for the PPP connection's TCP/IP protocol. The Java code in the Windows client will then provide the server with the correct (dynamically assigned) IP host name.

When you access the Nways Web pages, your browser may ask if you want to allow unsigned applets. To use the Web functions of the Nways Manager, you must allow unsigned applets.
Note:If you are using the HotJava(TM) Browser, you must start it using the following parameters: 
hotjava -mx64M

Remote Monitor

Before you can use Remote Monitor, you must set the RMONHOME environment variable to point to:

/usr/LANReMon/rmon

To set the RMONHOME environment variable in your .profile and add it to your default path, add the following lines to your .profile:

RMONHOME=/usr/LANReMon/rmon

export RMONHOME

PATH=$RMONHOME:$PATH

export PATH

DB2 Universal Database

Performance management for these device managers uses a Java Database Connectivity (JDBC)-compliant database. For your convenience, DB2 Universal Database(R) is provided.

You will need to create a database instance that can be accessed using JDBC by the device managers. The steps explaining how to create a database instance using DB2(R) with Nways Manager for HP-UX (the concept is the same if you are using another JDBC-compliant database, but you will need to refer to that database's instructions) can be found in the Nways Manager Element Manager User's Guide.

Using Web Servers

Before you can use the various web servers to configure Nways Manager, you must install the following web server settings. All web servers have to be configured to listen to the client on port 80 (which is the default port for most of the servers).

Apache Server

  1. Add the following lines in the given order to the file:



    		/Server_root/cpnf/srm.conf.

    		Alias /nways "/usr/CML/JMA/java/webservr"

    		Alias /cgi/code "/usr/CML/JMA/java/webservr/code"

    		ScriptAlias /cgi "/usr/CML/JMA/java/webservr"


    		Server_root - The directory where the Apache Websvr is installed.

    		usr - The directory where the Nways product is installed.

Netscape Server

  1. Go to the server main page and check whether the server is ON.
  2. Select Programs menu from the top of the page.
  3. Select CGI File Type.
  4. Select Yes for Activate CGI as a file type.
  5. Select Content Management from the top menu.
  6. Select Additional Document Directories, and add the following lines:

    		URL prefix: nways

    		Map to directory: /usr/CML/JMA/java/websvr



    		URL prefix: cgi

    		Map to directory: /usr/CML/JMA/java/websvr

Domino Web Server

  1. Go to http://Machine/Frntpage.html (machine where you have installed the Domino Web Server).
  2. Select Configuration and Administration Forms. 
                 (http://Machine/admin-bin/Cfgin/initial)
  3. Select Request Routing. 
                 (http://Machine/admin-bin/Cfgin/mpfrule)
  4. Add the following lines in the given order:
    Action Request Template Replacement File Path
    Pass /nways/* /usr/CML/JMA/java/websvr/*
    Exec /cgi/CgiLauncher* /usr/CML/JMA/java/websvr/CgiLauncher*
    Pass /cgi/* /usr/CML/JMA/java/websvr/*



[ Top of Page | Previous Page | Next Page | Table of Contents ]